Skip to content

Update throttling-limits.md #9327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Apr 30, 2024
Merged

Update throttling-limits.md #9327

merged 3 commits into from
Apr 30, 2024

Conversation

rpakala-ms
Copy link
Contributor

Updating Base Resource Unit Cost for directoryObjects/getByIds and getObjectsById from 3 to 5.

Also, a note stating: "Using $select for directoryObjects/getByIds and getObjectsById decreases cost by 2"

Instructions: Add any supporting information, such as a description of the PR changes, here.

Note

The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.

After you've created your PR, expand this section for tips and additional instructions.
  • do not merge is the default PR status and is automatically added to all open PRs that don't have the ready to merge label.
  • Add the ready for content review label to start a review. Your PR won't be reviewed until you add this label.
  • If your content reviewer requests changes, review the feedback and address accordingly as soon as possible to keep your pull request moving forward. After you address the feedback, remove the changes requested label, add the review feedback addressed label, and select the Re-request review icon next to the content reviewer's alias. If you can't add labels, add a comment with #feedback-addressed to the pull request.
  • After the content review is complete, your reviewer will add the content review complete label. When the updates in this PR are ready for external customers to use, replace the do not merge label with ready to merge and the PR will be merged within 24 working hours.
  • Pull requests that are inactive for more than 6 weeks will be automatically closed. Before that, you receive reminders at 2 weeks, 4 weeks, and 6 weeks. If you still need the PR, you can reopen or recreate the request.

For more information, see the Content review process summary.

@rpakala-ms
Update throttling-limits.md
47dd4d7 
Updating Base Resource Unit Cost for directoryObjects/getByIds and getObjectsById from 3 to 5.

Also, a note stating: "Using $select for directoryObjects/getByIds and getObjectsById decreases cost by 2"
@learn-build-service-prod Learn Build Service (PROD)
Copy link

Learn Build status updates of commit 47dd4d7:

✅ Validation status: passed

File Status Preview URL Details
concepts/throttling-limits.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Lauragra
Copy link
Contributor

@rpakala-ms , this PR is in a draft state; would you like us to publish it or is there a reason to wait?

@learn-build-service-prod Learn Build Service (PROD)
Copy link

Learn Build status updates of commit c5df029:

✅ Validation status: passed

File Status Preview URL Details
concepts/throttling-limits.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@rpakala-ms
Update throttling-limits.md
5e14e07 
updated based on confirmation from Neehar Mandaram(nemandar@microsoft.com)
@rpakala-ms
Copy link
Contributor Author

@rpakala-ms , this PR is in a draft state; would you like us to publish it or is there a reason to wait?

@Lauragra - pushed another commit for minor fix, should be good to publish, thankyou!

@rpakala-ms rpakala-ms marked this pull request as ready for review April 25, 2024 00:52
@learn-build-service-prod Learn Build Service (PROD)
Copy link

Learn Build status updates of commit 5e14e07:

✅ Validation status: passed

File Status Preview URL Details
concepts/throttling-limits.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@rpakala-ms
Copy link
Contributor Author

@Lauragra could you please publish the change to main, please let me know if there are any questions.
Thanks in advance!

@Lauragra Lauragra added ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master. and removed awaiting internal response labels Apr 29, 2024
@Lauragra Lauragra merged commit ef336a8 into microsoftgraph:main Apr 30, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
ready to merge Use this label to indicate to the repository admins that your PR is ready to merge into master.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rpakala-ms @Lauragra